Associate Android Developer v1.0
Question 1
When your code execution reaches the breakpoint, Android Studio pauses execution of your app. You can then use the tools in the Debugger tab to identify the
state of the app. With Step Into you can
- A. examine the object tree for a variable, expand it in the Variables view. If the Variables view is not visible
- B. evaluate an expression at the current execution point
- C. advance to the next line in the code (without entering a method)
- D. advance to the first line inside a method call
- E. advance to the next line outside the current method
- F. continue running the app normally
Answer : D
Question 2
When your code execution reaches the breakpoint, Android Studio pauses execution of your app. You can then use the tools in the Debugger tab to identify the
state of the app. With Evaluate Expression you can
- A. examine the object tree for a variable; expand it in the Variables view
- B. evaluate an expression at the current execution point
- C. advance to the next line in the code (without entering a method)
- D. advance to the first line inside a method call
- E. advance to the next line outside the current method
- F. continue running the app normally
Answer : B
Question 3
When your code execution reaches the breakpoint, Android Studio pauses execution of your app. You can then use the tools in the Debugger tab to identify the
state of the app. With Step Over you can
- A. examine the object tree for a variable; expand it in the Variables view.
- B. evaluate an expression at the current execution point
- C. advance to the next line in the code (without entering a method)
- D. advance to the first line inside a method call
- E. advance to the next line outside the current method
- F. continue running the app normally
Answer : C
Question 4
When your code execution reaches the breakpoint, Android Studio pauses execution of your app. You can then use the tools in the Debugger tab to identify the
state of the app. With Step Out you can
- A. examine the object tree for a variable; expand it in the Variables view. If the Variables view is not visible
- B. evaluate an expression at the current execution point
- C. advance to the next line in the code (without entering a method)
- D. advance to the first line inside a method call
- E. advance to the next line outside the current method
- F. continue running the app normally
Answer : E
Question 5
The Log class allows you to create log messages that appear in logcat. Generally, you could use the following log methods: (Choose five.)
- A. Log.e(String, String) (error)
- B. Log.a(String, String) (all outputs)
- C. Log.w(String, String) (warning)
- D. Log.i(String, String) (information)
- E. Log.q(String, String) (questions)
- F. Log.d(String, String) (debug)
- G. Log.v(String, String) (verbose)
Answer : ACDFG
Question 6
Filter logcat messages. If in the filter menu, a filter option "Show only selected application"? means:
- A. Display the messages produced by the app code only (the default). Logcat filters the log messages using the PID of the active app.
- B. Apply no filters. Logcat displays all log messages from the device, regardless of which process you selected.
- C. Create or modify a custom filter. For example, you could create a filter to view log messages from two apps at the same time.
Answer : A
Question 7
Filter logcat messages. If in the filter menu, a filter option "Edit Filter Configuration"? means:
- A. Display the messages produced by the app code only (the default). Logcat filters the log messages using the PID of the active app.
- B. Apply no filters. Logcat displays all log messages from the device, regardless of which process you selected.
- C. Create or modify a custom filter. For example, you could create a filter to view log messages from two apps at the same time.
Answer : C
Question 8
The Layout Inspector in Android Studio allows you to compare your app layout with design mockups, display a magnified or 3D view of your app, and examine details of its layout at runtime. When this is especially useful?
- A. when your layout is built entirely in XML rather than runtime and the layout is behaving expectedly.
- B. when your layout is built at runtime rather than entirely in XML and the layout is behaving unexpectedly.
Answer : B
Question 9
If you want the Database Inspector to automatically update the data it presents as you interact with your running app, check the Live updates checkbox at the top of the inspector window. While live updates are enabled, what happens with the table in the inspector window?
- A. It is still editable. You can modify data in a table by double-clicking a cell, typing a new value, and pressing Enter.
- B. It becomes read-only and you cannot modify its values.
- C. It becomes read-only, but you cannot see its updated values before updating the data by clicking the Refresh table button at the top of the inspector window.
Answer : B
Question 10
Enable debugging on your device: If you are using the emulator, this is enabled by default. But for a connected device, you need to
- A. enable transfer data from the device in usb connection options.
- B. enable debugging in the device developer options.
- C. enable connection in bluetooth options.
Answer : B
Question 11
To run a debuggable build variant you must use a build variant that includes
- A. minifyEnabled false in the build configuration
- B. debuggable true or debuggable false in the build configuration
- C. debuggable true in the build configuration
Answer : C
Question 12
About running a debuggable build variant. Usually, you can just select the default "debug" variant that's included in every Android Studio project (even though it's not visible in the build.gradle file). But if you define new build types that should be debuggable, you must add "˜debuggable true' to the build type. Is that mostly true?
- A. Yes.
- B. No, if you define new build types that should be debuggable, you must add "˜debuggable false"™
- C. No, the debug variant should be visible in the build.gradle file anyway.
Answer : A
Question 13
With a room database. When performing queries, you'll often want your app's UI to update automatically when the data changes. Can you use a return value of type LiveData in your query method description to achieve this?
- A. Yes
- B. No
Answer : A
Room generates all necessary code to update the LiveData when the database is updated.
Question 14
As an example. Our MutableLiveData<Long> object, named mLapseTime, is not connected to a Room database, etc. How can we change the value in mLapseTime?
- A. mLapseTime.postValue("new String")
- B. mLapseTime.setValue(1000l)
- C. mLapseTime.changeValue(1000l)
Answer : B
Question 15
Interface for a callback to be invoked when a shared preference is changed. Interface is named:
- A. android.content.SyncStatusObserver
- B. android.content.SharedPreferences.Editor
- C. android.content.SharedPreferences.OnSharedPreferenceChangeListener
- D. android.content.SharedPreferences
Answer : C